Unattended runtime upgrade

Instead of upgrading basic runtimes, runtime clusters, or runtime clouds through the Boomi Integration user interface, you can do an unattended upgrade using the command line.

In either Windows or Linux, open a command prompt and use the commands to upgrade your basic runtime, runtime cluster, or runtime cloud. Having the system command option is beneficial when you want to automate the upgrade process.

The system where you upgrade a runtime must meet the applicable system requirements.

This upgrade method uses the unattended mode option (-q)of the install4j installer.

Important

Only the node that runs upgrades (typically the head node) restarts automatically to run the updated Java version. Therefore, you must restart all other nodes within the cluster to install the upgrade.

The following variable is commonly included in the command-line code:

• jvmCertsPath - (Optional) Specifies the JRE directory containing certificates to migrate to the upgraded JRE version.

For a complete list of the command-line options for the install4j installer, see Command-Line Options For Generated Installers.

Command-line code samples

The following example shows a sample Linux command for upgrading a basic runtime. The -console option displays status messages on the console from which to invoke the upgrade:

./atom_upgrade64.sh -q -console -dir /home/<username>/<atom_installation_directory>

The following example shows a sample Linux command for upgrading a runtime cluster:

./molecule_upgrade64.sh -q -console  -dir /home/<username>/<molecule_installation_directory>

The following example shows a sample Linux command for upgrading a runtime cloud:

./cloud_upgrade64.sh -q -console -
-dir /home/<username>/<cloud_installation_directory>

The following example shows a sample Linux command for upgrading a basic runtime to include migrating certificates from the previous JRE:

./atom_upgrade.sh -q -console -VjvmCertsPath=/home/<username>/<atom_installation_directory>/jre -dir /home/<username>/<atom_installation_directory>

note

For Windows, you can modify the examples by changing .sh to .exe.

The following examples show sample Linux commands for upgrading a basic runtime, runtime cluster, or runtime cloud. to include choosing how you want to update the JRE or use an external JDK.

• Switch the preferred JRE to the installation's JRE directory:

  ./atom_upgrade64.sh -q -console VprefJreLocation=internal -dir /home/<username>/<atom_installation_directory>

• Do not make changes to the preferred JRE (default)

  ./atom_upgrade64.sh -q -console VprefJreLocation=current -dir /home/<username>/<atom_installation_directory>

  If you don't include VprefJreLocation in the command, it defaults to current.

• Use an external JDK for preferred JRE:

  ./atom_upgrade64.sh -q -console VprefJreLocation=external -VexternalJDKPath = <external_JDK_path> -dir /home/<username>/<atom_installation_directory>

  If you set VprefJreLocation as external, you must also include VexternalJDKPath with the value set to the location of the JDK that you want to use.